-
Notifications
You must be signed in to change notification settings - Fork 1
[GPCAPIM-254]: API requests entry point #44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[GPCAPIM-254]: API requests entry point #44
Conversation
|
ALB Target: |
4 similar comments
|
ALB Target: |
|
ALB Target: |
|
ALB Target: |
|
ALB Target: |
|
ALB Target: |
2 similar comments
|
ALB Target: |
|
ALB Target: |
|
ALB Target: |
2 similar comments
|
ALB Target: |
|
ALB Target: |
gateway-api/src/gateway_api/get_structured_record/test_request.py
Outdated
Show resolved
Hide resolved
12056dd to
f53f1b2
Compare
…arding them on to the controller/handler to process.
da85110 to
b8f34ff
Compare
|
|
Deployment Complete
|



Description
Currently, an Lambda is handling the HTTP requests being passed through API Gateway. This will have a Flask app handle the requests, which will then forward them on to the controller/handler - GPCAPIM-255.
Context
In order for us to process request from consumer suppliers and forward them on to the provider supplier, we need to run a Flask app to make the relevant PDS and SDS retrievals for the given request. This introduces the front door to that Flask app.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.